Fix publish-nuget workflow: resolve signing key path to absolute#725
Merged
Conversation
Add 10.0.x to dotnet-version in codeql-analysis.yml to support building projects targeting net10.0.
The script passed a relative path (src/RulesEngine/signKey.snk) to -p:AssemblyOriginatorKeyFile, but MSBuild resolves that relative to the project directory, causing it to look for the file at src/RulesEngine/src/RulesEngine/signKey.snk which doesn't exist. Convert to absolute path using [System.IO.Path]::GetFullPath() so MSBuild finds the file at its actual location.
YogeshPraj
changed the title
sagarambilpure
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixing github action